Data control system for virtual environment

ABSTRACT

A data control system comprises a communication interface, a processing system, and a storage system. The communication interface is configured to receive a request to retrieve data from a primary storage volume that includes a secondary storage volume. The storage system is configured to store the primary storage volume that includes the secondary storage volume. The processing system is configured to identify changed segments of a plurality of segments in the primary storage volume and identify allocated segments of the changed segments. The communication interface is further configured to transfer the allocated segments in response to the request.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/406,333, entitled “DATA CONTROL SYSTEMS FOR VIRTUAL ENVIRONMENTS,”filed on Feb. 27, 2012; which is related to and claims priority to U.S.Provisional Patent Application No. 61/446,866 entitled “DATA CONTROLSYSTEM FOR VIRTUAL ENVIRONMENT” filed on Feb. 25, 2011, U.S. ProvisionalPatent Application No. 61/476,499 entitled “DATA CONTROL SYSTEM FORVIRTUAL ENVIRONMENT” filed on Apr. 18, 2011, and U.S. Provisional PatentApplication No. 61/478,497 entitled “DATA CONTROL SYSTEM FOR VIRTUALENVIRONMENT” filed on Apr. 23, 2011, which are all hereby incorporatedby reference in their entirety.

TECHNICAL BACKGROUND

In the field of computer hardware and software technology, a virtualmachine is a software implementation of a machine (computer) thatexecutes program instructions like a real machine. Virtual machinetechnology allows for the sharing of, between multiple virtual machines,the physical resources underlying the virtual machines.

In virtual machine environments, a hypervisor running on a host hardwaresystem creates a virtual system on which a guest operating system mayexecute. The virtual system includes a virtual storage volume on whichthe guest operating system stores its data. For example, the hypervisormay simulate a hard disk for the guest operating system that thehypervisor stores as a virtual disk file on the host system. Somehypervisors continually track and record changes to the virtual diskfile in a changed block list.

A virtual storage volume within a virtual machine contains data itemsthat need to be accessed and scanned. In most cases, accessing theunderlying contents of a storage volume can be very resource-intensive,reducing the performance of a virtual machine and other operationswithin a virtual machine environment.

OVERVIEW

Disclosed is a data control system, a method of operating a data controlsystem, and one or more computer-readable storage media that, whenexecuted by the data control system, direct the data control system tooperate as described herein.

In an embodiment, a method comprises receiving a request to retrievedata from a primary storage volume that includes a secondary storagevolume, identifying changed segments of a plurality of segments in theprimary storage volume, identifying allocated segments of the changedsegments based on an allocation status of a plurality of data itemscontained in the secondary storage volume, wherein the plurality of dataitems correspond to the changed segments, and transferring the allocatedsegments in response to the request.

In some embodiments, the method further comprises generating a list ofqualified blocks based on the allocated segments of the changed segmentsidentified in the primary storage volume.

In some embodiments, the method further comprises reading a plurality ofdata blocks from the primary storage volume based on the list ofqualified blocks.

In some embodiments, the primary storage volume comprises a plurality ofblocks corresponding to a plurality of data items in a secondary storagevolume within the primary storage volume.

In some embodiments, the method further comprises, in response to therequest to retrieve the data from the primary storage volume,determining a subset of the plurality of data items that are not livebased on the allocated segments of the changed segments identified inthe primary storage volume, and executing an operation on the subset ofthe data items to reduce an amount of the plurality of blocks involvedin retrieving the data.

In some embodiments, executing the operation on the subset of the dataitems to reduce the amount of the plurality of blocks involved inretrieving the data comprises deleting each data item of the subset ofthe data items.

In some embodiments, the method further comprises flushing changes tothe secondary storage volume after deleting each data item of the subsetof the data items.

In some embodiments, the primary storage volume includes a secondarystorage volume stored thereon, and identifying the allocated segments ofthe changed segments comprises identifying the allocated segments of thechanged segments based on an allocation status of a plurality of dataitems contained in the secondary storage volume, wherein the pluralityof data items correspond to the changed segments.

In another embodiment, a data control system comprises a communicationinterface, a processing system, and a storage system. The communicationinterface is configured to receive a request to retrieve data from aprimary storage volume that includes a secondary storage volume. Thestorage system is configured to store the primary storage volume thatincludes the secondary storage volume. The processing system isconfigured to identify changed segments of a plurality of segments inthe primary storage volume and identify allocated segments of thechanged segments. The communication interface is further configured totransfer the allocated segments in response to the request.

In another embodiment, one or more computer-readable storage media haveprogram instructions stored thereon for operating a data control system.The program instructions, when executed by the data control system,direct the data control system to receive a request to retrieve datafrom a primary storage volume. The program instructions further directthe data control system to identify changed segments of a plurality ofsegments in the primary storage volume, and to identify allocatedsegments of the changed segments. The program instructions furtherdirect the data control system to transfer the allocated segments inresponse to the request.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a data control system.

FIGS. 2A and 2B illustrate operations of a data control system.

FIG. 3 illustrates a data control system in an embodiment wherein a dataidentification module operates to identify segments in a primary storagevolume.

FIG. 4 illustrates a block mapping table.

FIG. 5 illustrates a data control system in a data transportenvironment.

FIG. 6 illustrates an operation of a data control system in a datatransport environment.

FIG. 7 illustrates a data control system in a virtual systemenvironment.

FIG. 8 illustrates a data control system in a data storage environment.

FIG. 9 illustrates an operation of a data control system in a datastorage environment.

FIG. 10 illustrates a data control system in a data storage environment.

FIG. 11 illustrates an operation of a data control system in a datastorage environment.

FIG. 12 illustrates a data control system in a virtual systemenvironment.

FIG. 13 illustrates a data control system in an exemplary embodiment.

DETAILED DESCRIPTION

The following description and associated figures teach the best mode ofthe invention. For the purpose of teaching inventive principles, someconventional aspects of the best mode may be simplified or omitted. Thefollowing claims specify the scope of the invention. Note that someaspects of the best mode may not fall within the scope of the inventionas specified by the claims. Thus, those skilled in the art willappreciate variations from the best mode that fall within the scope ofthe invention. Those skilled in the art will appreciate that thefeatures described below can be combined in various ways to formmultiple variations of the invention. As a result, the invention is notlimited to the specific examples described below, but only by the claimsand their equivalents.

Described herein are techniques for reducing storage I/O when performingmaintenance tasks such as backup, replication, or migration of virtualmachines. By leveraging these methods, data systems can alleviateunnecessary reads from an underlying or primary storage volume and readonly the segments required to perform the required maintenance tasks.

In particular, the systems and methods disclosed herein identify changedand live segments. The changed segments are determined using a changedblock list that is typically managed by a hypervisor. The correspondinglive segments are determined by identifying corresponding parts of thevirtual machine disk file and determining whether those correspondingparts are live. This task is typically accomplished by reading filesystem metadata from the Guest OS running on the virtual machine. Partsof the virtual machine disk file that are live are those parts that arein-use and not redundant. In this manner, the number of segments readfrom the primary storage volume is limited to those segments that havechanged and are live.

FIG. 1 illustrates data control system 100 according to an examplewhereby data control (DC) module 102 is implemented in order to identifysegments in a primary storage volume. Data control system 100 includesprocessing system 101, DC module 102, secondary storage volume 103, andprimary storage volume 105.

Processing system 101 comprises any system or collection of systemscapable of executing DC module 102 to identify segments in primarystorage volume 105. Processing system 101 may be a microprocessor, anapplication specific integrated circuit, a general purpose computer, aserver computer, or any combination or variation thereof. DC module 102may be program instructions executable by processing system 101.

Primary and secondary storage volumes 105 and 103, respectively, may beany storage volumes capable of storing a volume of data. Primary storagevolume 105 comprises segments 106. Secondary storage volume 103comprises data items 104. A data item may be, for example, a file. Dataitems 104 comprise the volume of data in secondary storage volume 103.Segments 106 comprise sections of a volume of data in primary storagevolume 105.

Secondary storage volume 103 may be a virtual storage volume on avirtual machine and data items 104 may comprise the virtual storagecontents of secondary storage volume 103. Secondary storage volume 103is itself stored within primary storage volume 105. Primary storagevolume 105 may be a virtual disk file. The virtual disk file comprises avolume of data that represents the contents of a virtual machine.Segments 106 may comprise sections of the volume of data in storagevolume 105.

In operation, processing system 101 running DC module 102 and/or primarystorage volume 105 track segments 106 of the data volume in storagevolume 105 that have changed. Similarly, processing system 101 runningDC module 102 and/or secondary storage volume 103 track whether dataitems 104 are live. Processing system 101 running DC module 102 thenidentifies and transfers those segments that are both live and havechanged in response to a request to retrieve data.

FIG. 2A illustrates process 200 describing the operation of data controlsystem 100 according to an example. To begin, one or more volumes ofdata are generated and stored. Processing system 101 receives a requestto retrieve data from primary storage volume 105 (Step 202). Processingsystem 101 running DC module 102 subsequently identifies changedsegments of a plurality of segments 106 in primary storage volume 105(Step 204). Processing system 101 running DC module 102 then identifiesallocated segments of the changed segments (Step 206) and transfers theidentified segments in response to the request (Step 208). Each segmentin primary storage volume can be changed or not changed and allocated(live) or free. Advantageously, this method provides for a way to limitthe number of segments read as only those segments that have changed andare allocated are read and/or transferred.

FIG. 2B illustrates process 210 describing the operation of data controlsystem 100 according to another example. To begin, one or more volumesof data is generated and stored. Processing system 101 receives arequest to retrieve data from primary storage volume 105 that includessecondary storage volume 103 (Step 212). For example, processing system101 running DC module 102 may receive a request to retrieve datarepresenting a virtual machine or virtual appliance. In this case,primary storage volume 105 comprises a virtual disk file which furthercomprises the volume of data that represents a virtual machine.Secondary storage volume 103 comprises a virtual storage volume on thevirtual machine.

Processing system 101 running DC module 102 subsequently identifieschanged segments of a plurality of segments 106 in primary storagevolume 105 (Step 214). For example, in response to the request toretrieve the volume of data from primary storage volume 105, processingsystem 101 running DC module 102 obtains a change segment list from ahypervisor and processes the change segment list to identify thesegments of segments 106 in primary storage volume 105 that havechanged. In this case, the change segment list is obtained from andmanaged by a hypervisor on which the virtual machine (corresponding tothe v-disk file) is running. Other elements may alternatively oradditionally manage the change segment list.

Processing system 101 running DC module 102 then identifies allocatedsegments of the changed segments based on an allocation status of aplurality of data items contained in secondary storage volume 103,wherein the plurality of data items correspond to the changed segments(Step 216). For example, processing system 101 running DC module 102reads the file system metadata from the Guest OS on the virtual machineto determine which parts of secondary storage volume 103 are redundantor no longer in use. More specifically, processing system 101 running DCmodule 102 identifies the data items of data items 104 that correspondto the changed segments and filters out those data items that are notlive. The file metadata may represent the status of the data items whichmay be stored in a file system having any number of formats such as, forexample, FAT, NTFS, HFS, UFS, ext2, ext3, ext4, VMFS, and the like.

In other examples, processing system 101 running DC module 102 reads thefile system metadata from locations other than the Guest OS such as aGuest Application running on the virtual machine or another entitywithin the virtual machine. Moreover, in some examples, processingsystem 101 running DC module 102 may determine the allocation statususing the hypervisor or other software on storage system 303.

By filtering out those data items that are not live (e.g., those dataitems that are redundant or no longer in use by the Guest O/S),processing system 101 running DC module 102 is left with those changedsegments that also correspond to live data items. Lastly, processingsystem 102 transfers the allocated segments in response to the request(Step 218). Those skilled in the art will appreciate that the transfers,as referred to herein, are typically not literal transfers. Rather, aversion of the segments may be transferred or copied. However, in someembodiments, the segments may literally be transferred.

Those skilled in art will also appreciate that data requests may be usedfor a variety of applications and/or data utilities. For example, a datautility may make the data request in order to backup, replicate, ormigrate virtual machines. Similarly, the data utility may make therequest to scan the data for viruses, to identify changed data items forcomputer or data forensics, for compliance needs, or in order to logsystem changes. It should be understood that data the request may bemade by a human operator or another software application, hardwareelement, or the like.

FIG. 3 illustrates data control system 300 in an embodiment wherein datacontrol module 350 operates to identify segments in primary storagevolume and transfer those segments. In this example, data storage system300 includes processing system 301, and storage system 303. Hypervisor305 runs on storage system 303. Virtual disk files 319 and 329 and DCmodule 350 run on hypervisor 305. As shown, DC module 350 runs onhypervisor 305, however in some embodiments, DC module 305 may rundirectly on storage system 303 or on another hypervisor (not shown)running on storage system 303 or another storage system (not shown).

Hypervisor 305 keeps track of those segments that have changed using achanged block list 304. In this example, segments are equivalent toblocks. The changed block list describes the blocks that have changed invirtual disk files 319 and 329. In some example, hypervisor 305generates changed block list 304. Those skilled in the art willappreciate that changed block list 304 may alternatively or additionallybe generated by any entity within virtual machine 309 (such as guestoperating system 313), processing system 301, and/or storage system 303.Moreover, changed block list 304 may be generated by replicationsoftware, continuous data protection (CDP) software, or virtual diskchange block tracking software running on virtual machine 309,hypervisor 305, or processing system 301.

Virtual disk files 319 and 329 may be, for example, VMWare images (.vmdkfiles), VirtualBox images (.vdi files), Virtual Hard Disk images (.vhd),and/or other image format files, including combinations thereof. Virtualdisk files 319 and 329 include block mapping tables. Block mapping table320 describes the storage of the data volume in virtual disk file 319.For example, block mapping table 320 may describe the correspondencebetween data items on virtual storage volume 316 and underlying virtualdisk file 319. Block mapping table 320 is shown with more detail in FIG.4.

As discussed, hypervisor 305 includes virtual machines represented byv-disk files 319 and 329. In particular, v-disk file 319 representsvirtual machine 309. Virtual machine 309 includes guest operating system313 and virtual hardware 315. Guest operating system 313 includesmetadata 312. Virtual hardware 315 includes virtual storage volume 316,virtual processor 317, and virtual peripheral 318.

In operation, processing system 301, executing software including DCmodule 350, identifies and transfers live and changed segmentscorresponding to requested segments. As shown in this example,processing system 301 receives a request to retrieve data from virtualdisk file 319. In particular, in this example, all of the segments ofvirtual disk file 319 are requested (i.e., segments A, B, C, and D).

Processing system 301 executing DC module 350 first identifies changedsegments of the plurality of segments in the primary storage volume. Inthis example, the primary storage volume comprises virtual disk file319. The changed block list 304 indicates that blocks A and B havechanged.

Processing system 301 executing DC module 350 subsequently identifiesallocated segments of the identified changed segments based on anallocation status of a plurality of data items contained in virtualstorage volume 316, wherein the plurality of data items correspond tothe changed segments. The block mapping table 320 and metadata 312 areaccessed to accomplish this task. For example, FIG. 4 illustrates thatchanged block A corresponds to data item D1 and changed block Bcorresponds to data item D2. Metadata 320 is accessed from guestoperating system 313 to determine the allocation status of data items D1and D2. In this example, only D1 is allocated or live, and thus onlysegment A is both changed and allocated. Processing system 301 executingDC module 305 then transfers segment A in response to the request.

Advantageously, DC module 350 understands the multiple layers of data ina control system 300 as a group and when reading the virtual machines(segments from virtual disk representing the virtual machine data), onlythe data actually in use at the time of the read is transferred. This isthe case regardless of whether the data block was previously in use orchanged. The software reading the virtual disk, whether it be a backupagent or a replication tool, still receives a standard virtualdisk-formatted data stream, but the stream has been scrubbed clean ofrandom data. This process increases WAN throughput, compression, and/orde-duplication activities that occur after reading the virtual machine.

FIGS. 5 through 7 describe techniques for reducing storage I/O whenperforming tasks such as backup, replication, or migration of virtualmachine data. By leveraging these methods, data systems can alleviateunnecessary reads from a data volume and read only data blocks requiredto perform the required tasks. More specifically, qualified blocks in adata volume are identified in order to generate a qualified block list.The qualified block list identifies qualified blocks (e.g., those blocksthat are “live” or allocated in the data volume). In this manner, thenumber of data blocks read from the data volume is limited to qualifiedblocks identified in the qualified block list.

FIG. 5 illustrates data control system 510 in data transport environment500. Data transport environment 500 includes data request 505, datacontrol system 510, data volume 520, and data volume 525. Data controlsystem 510 includes null block module 514, DC module 515, and qualifiedblock (Q-block) list 517. Data volume 520 includes a block mapping table525.

Data control system 510 comprises any system or collection of systemscapable of executing DC module 515 to identify qualified blocks in datavolume 520 and to responsively generate a list of the identifiedqualified blocks. Data control system 510 may be a microprocessor, anapplication specific integrated circuit, a general purpose computer, aserver computer, or any combination or variation thereof. DC module 515may be program instructions executable by processing system. Null blockmodule 514 may be, for example, a special file (or module) called“/dev/zero.” The “/dev/zero” file normally resides in Unix-likeoperating systems. Typically, the file provides as many null characters(ASCII NUL, 0x00) as are read from it.

Data volume 520 may be any storage volume capable of storing a volume ofdata, wherein the volume of data comprises a plurality of data blocks.For example, data volume 520 may be a virtual disk file. Virtual diskfiles may be, for example, VMware images (.vmdk files), VirtualBoximages (.vdi files), Virtual Hard Disk images (.vhd), and/or other imageformat files, including combinations thereof. In this case, the virtualdisk file includes block mapping table 525.

Block mapping table 525 describes the storage of data in data volume 520(e.g., in the virtual disk file). For example, block mapping table 525may describe data blocks A, B, C, D, E, and F and their correspondencewith data items or files. More importantly, the block mapping table maybe used to identify which of the blocks are “live.” As shown in FIG. 5,data volume 520 includes data blocks A, B, C, D, E, and F. Qualifiedblocks B, C, E, and F are those data blocks that are “live” (i.e.,allocated) in data volume 520. The qualified blocks are shown withoutshading. Blocks A and D are not “live,” and thus are shown shaded.

In operation, DC module 515 is implemented to direct data control system510 to identify qualified blocks in a data volume in response to datarequest 505. For example, data request 505 may request an entire datavolume 520 (i.e., each of the data blocks in data volume 520). Datacontrol system 510 then generates Q-block list 517 identifying only thequalified blocks in data volume 520 and uses Q-block list 517 todetermine which blocks to request from data volume 520. Advantageously,data volume 520 receives a request for, and returns, only the requested(or read) blocks reducing the amount of data that needs to be accessedfrom data volume 520.

FIG. 6 illustrates process 600 describing operation of data controlsystem 510 in data transport environment 500. To begin, data controlsystem 510 receives a data open request for a first volume of datahaving a first plurality of data blocks (Step 602). In some examples,the data open request may be a file open request. For example, datacontrol system 510 may present itself to a data utility (not shown) overa network (LAN or WAN) as a shared disk. The data utility can thenrequest to mount or map the drive in order to see information regardingdata volume 520. When mounted or mapped, data control system 510 mayprovide a file system view of data volume 520 and other data volumes(not shown) to the data utility.

Data control system 510 then identifies qualified blocks of the firstplurality of data blocks (604). The qualified blocks comprise datablocks that are live blocks. For example, responsive to receiving thedata open request, data control system 510 may access block mappingtable 525 which describes the storage of the data volume 520. Blockmapping table 525 describes data blocks A, B, C, D, E, and F and theircorrespondence with data items or files. More importantly, the blockmapping table is used to identify which of the blocks are “live.” Inthis example, data blocks B, C, E, and F are “live” data blocks. Thoseskilled in the art will appreciate that identifying the liveliness ofthe data blocks may also require access to file system metadata in aguest O/S (discussed in more detail with respect to FIG. 13).

Data control system 510 filters the plurality of data blocks toconstruct a list of qualified blocks (Step 606). For example, datablocks A and D are not “live,” and thus are filtered out. Once the listof qualified blocks is constructed or generated, data control system 510reads the list of qualified blocks from the first volume of data (Step608). In this example, data control system 510 requests or readsqualified blocks B, C, E, and F using the constructed qualified-blocklist 517.

Data control system 510 then reads the remaining blocks (i.e., thenon-qualified blocks) from null block module 514 (Step 610). Asdiscussed above, null block module 514 may be a “/dev/zero” file thatprovides as many null characters (ASCII NUL, 0x00) as are read from it.In this example, the remaining or non-qualified blocks A and D are readfrom /dev/zero file. Lastly, data control system 510 transfers a secondvolume of data comprising the qualified blocks received from data volume520 and the null blocks provide by the null block module 514 (Step 612).

FIG. 7 illustrates an embodiment wherein the data control system isembedded in a virtual system environment 700. In this example, datacontrol module 750 operates to identify qualified blocks in a datavolume in response to a data request. Virtual system environment 700includes processing system 701, and storage system 703. Hypervisor 705runs on storage system 703. Virtual disk files 719 and 729 and DC module750 run on hypervisor 705. As shown, DC module 750 runs on hypervisor705, however in some embodiments, DC module 750 may run directly onstorage system 703, on another hypervisor (not shown) running on storagesystem 703, and/or on another storage system (not shown). Although notshown in this example, those skilled in the art will appreciate that insome embodiments DC module 750 may run on storage systems outside ofvirtual system environment 700.

Hypervisor 705 keeps track of those data blocks that have changed usinga changed block list 704. Changed block list 704 describes the blocksthat have changed in virtual disk files 719 and 729. In some example,hypervisor 705 generates changed block list 704. Those skilled in theart will appreciate that changed block list 704 may alternatively oradditionally be generated by any entity within virtual machine 709 (suchas guest operating system 713), processing system 701, and/or storagesystem 703. Moreover, changed block list 704 may be generated byreplication software, continuous data protection (CDP) software, orvirtual disk change block tracking software running on virtual machine709, hypervisor 705, or processing system 701.

Virtual disk files 719 and 729 may be, for example, VMWare images (.vmdkfiles), VirtualBox images (.vdi files), Virtual Hard Disk images (.vhd),and/or other image format files, including combinations thereof. Virtualdisk files 719 and 729 include block mapping tables. Block mapping table720 describes the storage of the data volume in virtual disk file 719.For example, block mapping table 720 may describe the correspondencebetween data items (D1, D2, and D3) on virtual storage volume 716 andunderlying virtual disk file 719. More importantly, the block mappingtable may be used to identify which of the blocks are “live.”

As discussed, hypervisor 705 includes virtual machines represented byv-disk files 719 and 729. In particular, v-disk file 719 representsvirtual machine 709. Virtual machine 709 includes guest operating system713 and virtual hardware 715. Guest operating system 713 includesmetadata 712. Virtual hardware 715 includes virtual storage volume 716,virtual processor 717, and virtual peripheral 718.

In operation, processing system 701, executing software including DCmodule 750, receives a request for a volume of data having a pluralityof data blocks. In this example processing system 701 receives a requestfor v-disk 719. As shown, v-disk 719 comprises data blocks A, B, C, andD. Processing system 701 executing DC module 750 then identifiesqualified blocks of the plurality of data blocks in v-disk 719. In thisexample, the qualified blocks are those data blocks that are live.However, in other examples, the qualified blocks may be data blocks thatare both live and that have changed. Other criteria for identifyingqualified blocks are also possible.

Processing system 701 executing DC module 750 subsequently filters theplurality of data blocks to construct Q-block list 751 identifying thequalified blocks to be read. In this example, Q-block list 751 includesqualified blocks C and D. Processing system 701 executing DC module 750then reads the qualified blocks based on the Q-block list 751 fromv-disk 719. As discussed, accessing the underlying contents of a storagevolume (v-disk 719) can be very resource intensive, reducing theperformance of a virtual machine and other operations within a virtualmachine environment. Advantageously, in this example, only blocks C andD need to be read from v-disk 719.

In order to return a full v-disk, as typically requested, processingsystem 701, executing DC module 750, reads the remaining blocks (i.e.,the non-qualified blocks) from a “/dev/zero” file that provides as manynull characters (ASCII NUL, 0x00) as are read from it. In this example,the remaining or non-qualified blocks A and B are read from the/dev/zero file. Lastly, processing system 701 executing DC module 750transfers a second v-disk (in response to the request for v-disk 719)comprising the qualified blocks received from data volume 520 and thenull blocks provided by the “/dev/zero” file.

FIGS. 8 through 12 describe techniques for reducing storage I/O whenperforming tasks such as backup, replication, or migration of virtualmachine data. By leveraging these methods, data systems can alleviateunnecessary reads from a data volume and read only data blocks requiredto perform the required tasks. More specifically, the number of blocksinvolved in a primary operation may be reduced by determining a statusof each corresponding data item and executing a secondary operation on asubset of the plurality of data items. In this manner, the number ofdata blocks read from the data volume is limited to active (i.e.,non-deleted) blocks in the primary storage volume.

FIG. 8 illustrates data control system 810 in data storage environment800. Data storage environment 800 includes instruction 805, data controlsystem 810, and storage environment 820. Storage environment 820includes primary storage volume 821 and secondary storage volume 822.Data control system 810 includes DC module 815.

Data control system 810 comprises any system or collection of systemscapable of executing DC module 815 to direct data control system tooperate as described herein. Data control system 810 may be amicroprocessor, an application specific integrated circuit, a generalpurpose computer, a server computer, or any combination or variationthereof. DC module 815 may be program instructions executable byprocessing system.

Storage environment 820 comprises any system of collection of systemsthat includes one or more storage volumes. As discussed, storageenvironment 820 includes primary storage volume 821 and secondarystorage volume 822. Primary and secondary storage volumes 821 and 822,respectively, may be any storage volumes capable of storing volumes ofdata. Primary storage volume 821 comprises blocks A, B, C, D, E, and F.One or more of blocks A, B, C, D, E, and F may comprise secondarystorage volume 822. In this example, blocks A, B, C, D, E, and Fcomprise secondary storage volume 822. Secondary storage volume 822comprises data items D1, D2, D3, D4, D5, and D6. Data items data itemsD1, D2, D3, D4, D5, and D6 comprise the volume of data in secondarystorage volume 822. For simplicity, in this example each data itemcorresponds to a single block. However, those skilled in the art willappreciate that a data item may correspond to more than one block.Likewise, in some cases, multiple data blocks correspond to a singleblock.

A block mapping table (not shown for simplicity) may be used by storageenvironment 820 to describe the relationship between primary storagevolume 821 and secondary storage volume 822. In this example, block A ofprimary storage volume 821 corresponds to data item D1 of secondarystorage volume 822, block B corresponds to data item D2, and so on.

In operation, data control system 810 receives instruction 805 toperform a primary operation on primary storage volume 821 andresponsively reduces the number of allocated or “live” blocks in primarystorage volume 821. The reduction of blocks occurs as a result of thedeletion of corresponding data items in secondary storage volume 822.For example, data items D1 and D4 are shown shaded because theyrepresent data items that are not “live” or allocated. Unallocated dataitems may comprise system files such as, for example, cache files, ghostfiles, and swap files. Advantageously, reducing the number of allocatedor “live” blocks in primary storage volume 821 may result in fewerblocks needing to read in order to complete the primary operation onprimary storage volume 821.

FIG. 9 illustrates process 900 describing operation of data controlsystem 810 in data transport environment 800. To begin, data controlsystem 810 receives instruction 805 (Step 902). In response to theinstruction, DC module 815 is implemented to direct data control system810 to initiate a primary operation on primary storage volume 821. Asdiscussed, primary storage volume 821 comprises a plurality of blockscorresponding to a plurality of data items in secondary storage volume822. The primary operation may be, for example, a request to readprimary storage volume 821.

In response to the instruction to initiate the primary operation, DCmodule 815 is implemented to direct data control system 810 to reducethe plurality of blocks involved in the primary operation by determininga status of each of the plurality of data items and executing asecondary operation on each of a subset of the plurality of data items(Step 904). For example, data control system 810 may determine theliveliness status of each of the plurality of data items by accessingmetadata (not shown) associated with secondary storage volume 822. Thesecondary operation may be, for example, an operation to delete thesubset of the plurality of items that are not live or unallocated. Inthis example, data control system 810 directs storage environment 820 todelete data items D1 and D4 from secondary storage volume 822 resultingin the deletion of blocks A and D, respectively, from primary storagevolume 821.

FIG. 10 illustrates data control system 1010 in data storage environment1000 for accessing elements and/or contents of virtual systemenvironment 1020. Data storage environment 1000 includes data controlsystem 1010, virtual system environment 1020, and data utility 1040.Data utility 1040 is in communication with data control system 1010.Data control system 1010 is in communication with virtual systemenvironment 1020.

Data control system 1010 comprises any system or collection of systemscapable of executing a DC module (not shown) to direct data controlsystem 1010 to operate as described herein. Data control system 1010 maybe a microprocessor, an application specific integrated circuit, ageneral purpose computer, a server computer, or any combination orvariation thereof. DC module may be program instructions executable by aprocessing system on data control system 1010. In this example, dataidentification system 1010 is shown outside virtual system environment1020. However, those skilled in the art will appreciate that in someembodiments, data identification system 1010 may be located withinvirtual system environment 1020.

Virtual system environment 1020 comprises real machine 1021. Realmachine 1021 may be may be any computer system, custom hardware, orother device. Real machine 1021 includes a storage system for storingsoftware, and may retrieve and execute software from the storage system.The storage system could include a computer-readable medium such as adisk, tape, integrated circuit, server, or some other memory device, andalso may be distributed among multiple memory devices. Each real machine1021 acts as a host machine. In this example, one host machine is shownfor simplicity. Those skilled in the art will appreciate that any numberof host machines may be included in virtual system environment 1020.Real machine 1021 comprises hypervisor 1022. Hypervisors allow multipleoperating systems to run concurrently on real machine 1021 (i.e., thehost machine). In this example a single hypervisor (i.e., hypervisor1022) is shown for simplicity. Those skilled in the art will appreciatethat more hypervisors may be present on each real machine 1021.

As shown, hypervisor 1022 includes a single virtual disk file 1023 forsimplicity. Those skilled in the art will appreciate that more than onevirtual disk file may be present on each hypervisor. Virtual disk file1023 may be, for example, VMWare images (.vmdk files), VirtualBox images(.vdi files), Virtual Hard Disk images (.vhd), and/or other image formatfiles, including combinations thereof. Virtual disk file 1023 comprisesa plurality of blocks A-F which together comprise one or more secondarystorage volumes. In this example, blocks A-C comprise virtual drive1024X and blocks D-F comprise virtual drive 1024Y. Virtual drive 1024Xcomprises a plurality of data items D1-D3. Likewise, virtual drive 1024Ycomprises a plurality of data items D4-D6. As discussed, the data itemsmay be files on the virtual drives such as, for example, cache files,ghost files, swap files, operating system files, regular files, and thelike.

Typically, virtual disk file 1023 also includes a block mapping table.The block mapping table describes the storage on virtual disk file 1023.For example, the block mapping table may describe the correspondencebetween data items D1-D6 on virtual disk 1024X and 1024Y and theunderlying virtual disk file 1023.

Data utility may 1040 may comprise any of a variety of applications orappliances. For example, data utility 1040 may be compliance software,security software, backup software, log analytics software, replicationsoftware, and/or patch management software.

In operation, data control system 1010 may first present itself to datautility 1040 over a network (LAN or WAN) as a shared disk. For example,data utility 1040 may see “P:\” (or a P-DRIVE). Data utility 1040 canthen request to mount or map the P-DRIVE. In this example, in responseto receiving the request to mount, data identification system 610identifies processing elements, virtual processing elements, virtualstorage elements, and contents of virtual storage elements and generatesa file system view comprising the identified elements arranged in ahierarchical order. In this way, data control system 1010 emulates aphysical drive by allowing the data utility to mount or map a drive tothe elements and contents of storage environment 1020.

Once mounted or mapped, data control system 1010 provides the filesystem view to data utility 1040. Data utility may then access requestaccess to the contents of virtual system environment 1020.

FIG. 11 illustrates process 1100 describing operation of data controlsystem 1010 in virtual system environment 1000. More specifically, thisexample illustrates triggering pre-processing scripts in data controlsystem 1010 to perform a series of operations to reduce the number ofblocks that need to be read from virtual disk file 1023.

Those skilled in the art will appreciate that it is often necessary todo explicit operations on live data sources (e.g., virtual disk files ina virtual system environment) prior to accessing the data sources (e.g.,for backup or other operations) in order to guarantee data consistency.In some cases, a live data source may be put into logging mode prior tocopying the contents of the data source during the backup or otheroperation. Once the backup or other operation is complete, the datasource must then be taken out of logging mode so that the log can bemerged back into the database.

Typically, a data utility 1040 contains call out points that invoke pre-and post-processing scripts. These scripts are explicit operationscontrolled by data utility 1040. A pre-processing script is invokedprior to copying the data and a post-processing script is invoked aftercopying the data. However, rather than embedding the commands forinvoking the pre- and post-processing scripts and the scripts themselvesinto the backup software, these commands and scripts can be embeddedinto data control system 1010. In this way, the pre-processing scriptscan be invoked or triggered based on file open calls and post-processingscripts can be invoked or triggered based on file release calls. Byembedding commands and scripts into a data control system, datautilities do not need to be modified for each data source that requiresdata consistency and content generation operations.

To begin, data control system 1010 receives a request to open a virtualdisk file (Step 1102). In some examples, the data open request may be afile open request. For example, data control system 1010 may presentitself to a data utility (not shown) over a network (LAN or WAN) as ashared disk. The data utility 1040 may then request to mount or map thedrive in order to see information in virtual system environment 1020.When mounted or mapped, data control system 1010 may provides the filesystem view of virtual system environment 1020 to the data utility.

The request to open a virtual disk file may trigger one or morepre-processing scripts. For example, upon being presented the filesystem view including virtual disk file 1023, data utility 1040transfers a request to open virtual disk file 1023. As discussed, therequest to open a virtual disk file may be a request to read thecontents of virtual disk file 1023. In this example, pre-processingscripts are triggered when data control system 1010 receives the virtualdisk file open request. The pre-processing scripts direct data controlsystem 1010 to open the virtual disk file and identify non-live dataitems of the plurality of data items on the virtual drives (Step 1104).

In this example, non-live data items are shown shaded. Data item D3 onvirtual drive 1024X and data item D4 on virtual drive 1024Y are non-livedata items. As discussed, these non-live data items may be, for example,cache files, ghost files, or swap files. The liveliness of the dataitems may be determined by accessing the metadata in a guest operatingsystem. This is discussed in more detail with respect to FIG. 12.

Once the non-live data items are identified, data control system 1010deletes the identified non-live data items in virtual drives 1024X and1024Y and closes the virtual disk file to flush changes (Step 1106).Those skilled in the art will appreciate that deletion of the data itemsresults in deletion of corresponding blocks in virtual disk file 1023.As discussed, the data source must be taken out of logging mode so thatthe log can be merged back into the database—resulting in the flush.

The pre-processing scripts then direct data control system 1010 to openvirtual disk file 1023 again and read the active or “live” blocks (Step1108) and transfer the active blocks to the data utility (Step 1110).When completed, data utility 1040 may transfer a file release call todata control system 1010 triggering the post-processing scripts whichcloses the virtual disk file and flushes the changes, if any.

FIG. 12 illustrates an embodiment wherein the data control system isembedded in a virtual system environment 1200. In this example, datacontrol module 1250 operates to identify and delete non-live data itemsin a secondary storage volume in response to a data request. Virtualsystem environment 1200 includes processing system 1201, and storagesystem 1203. Hypervisor 1205 runs on storage system 1203. Virtual diskfiles 1219 and 1229 and DC module 1250 run on hypervisor 1205. As shown,DC module 1250 runs on hypervisor 1205. However, in some embodiments, DCmodule 1250 may run directly on storage system 1203, on anotherhypervisor (not shown) running on storage system 1203, and/or on anotherstorage system (not shown). Although not shown in this example, thoseskilled in the art will appreciate that in some embodiments DC module1250 may run on storage systems outside of virtual system environment1200.

Hypervisor 1205 keeps track of those data blocks that have changed usinga changed block list 1204. Changed block list 1204 describes the blocksthat have changed in virtual disk files 1219 and 1229. In some example,hypervisor 1205 generates changed block list 1204. Those skilled in theart will appreciate that changed block list 1204 may alternatively oradditionally be generated by any entity within virtual machine 1209(such as guest operating system 1213), processing system 1201, and/orstorage system 1203. Moreover, changed block list 1204 may be generatedby replication software, continuous data protection (CDP) software, orvirtual disk change block tracking software running on virtual machine1209, hypervisor 1205, or processing system 1201.

Virtual disk files 1219 and 1229 may be, for example, VMWare images(.vmdk files), VirtualBox images (.vdi files), Virtual Hard Disk images(.vhd), and/or other image format files, including combinations thereof.Virtual disk files 1219 and 1229 include block mapping tables. Blockmapping table 1220 describes the storage of the data volume in virtualdisk file 1219. For example, block mapping table 1220 may describe thecorrespondence between data items (D1, D2, and D3) on virtual storagevolume 1216 and underlying virtual disk file 1219.

As discussed, hypervisor 1205 includes virtual machines represented byv-disk files 1219 and 1229. In particular, v-disk file 1219 representsvirtual machine 1209. Virtual machine 1209 includes guest operatingsystem 1213 and virtual hardware 1215. Guest operating system 1213includes metadata 1212. Virtual hardware 1215 includes virtual storagevolume 1216, virtual processor 1217, and virtual peripheral 1218.

In operation, processing system 1201, executing software including DCmodule 1250, receives a request for a volume of data having a pluralityof data blocks. In this example processing system 1201 receives arequest for v-disk 1219. As shown, v-disk 1219 comprises data blocks A,B, C, and D. Processing system 1201 executing DC module 1250 opens thev-disk 1219 and accesses the guest O/S 1213 and/or metadata 1212 todetermine which data items are non-live. In this example, data item D1is shown shaded and thus, is non-live. Data item D1 is subsequentlydeleted and v-disk 1219 closed. Closing v-disk 1219 flushes the deleteddata item D1, and thus blocks A and B which correspond to data item D1are also deleted. As discussed, block mapping table 1220 identifieswhich blocks correspond to which data items in v-disk file 1219.

Processing system 1201, executing software including DC module 1250,then re-opens v-disk file 1219 and reads the active or live blocks. Inthis case, because blocks A and B have been deleted, only blocks C and Dare read. Advantageously, the number of blocks needed to be read andtransferred from virtual storage system 1200 is reduced.

FIG. 13 illustrates data control system 1300. Data control system 1300provides an example of data control system 100 of FIG. 1, data controlsystem 300 of FIG. 3, data control system 510 of FIG. 5, data control810 of FIG. 8, data control system 1010 of FIG. 10, although systems100, 300, 510, 810, and 1010 may use alternative configurations. Datacontrol system 1300 includes processing system 1313, user interface1312, and communication interface 1311. User interface 1312 may beexcluded in some embodiments. Processing system 1313 includes storagesystem 1314. Storage system 1314 stores software 1315. Processing system1313 is linked to user interface 1312 and communication interface 1311.Software 1315 includes data control (DC) module 1316. DC module 1316provides an example of DC module 102 of FIG. 1, DC module 350 of FIG. 3,DC module 515 of FIG. 5, DC module 750 of FIG. 7, DC module 815 of FIG.8, and DC module 1250 of FIG. 12, although DC modules 102, 350, 515,750, 815, and 1250 may use alternative configurations.

Data control system 1300 could be comprised of a programmedgeneral-purpose computer, although those skilled in the art willappreciate that programmable or special purpose circuitry and equipmentmay be used. Data control system 1300 may be distributed among multipledevices that together comprise elements 1311-1315.

Communication interface 1311 is configured to communicate with a storageenvironment including storage environment 820 and virtual systemenvironment 1020. Additionally, communication interface 1311 may beconfigured to communicate with one or more data utility or otherapplication which may, for example, mount or map data control system1300 to access a storage environment.

Communication interface 1311 could comprise a network interface, modem,port, transceiver, or some other communication device. Communicationinterface 1311 may be distributed among multiple communication devices.Processing system 1313 could comprise a computer microprocessor, logiccircuit, or some other processing device. Processing system 1313 may bedistributed among multiple processing devices.

User interface 1312 could comprise a keyboard, mouse, voice recognitioninterface, microphone and speakers, graphical display, touch screen, orsome other type of user device. User interface 1312 is configured tocommunicate with a system operator. As discussed, user interface 1312may be omitted in some embodiments.

Storage system 1314 could comprise a disk, tape, integrated circuit,server, or some other memory device. Storage system 1314 may bedistributed among multiple memory devices. Storage system 1314 includessoftware 1315. Software 1315 may include an operating system, logs,utilities, drivers, networking software, and other software typicallyloaded onto a computer system. Software 1315 could contain anapplication program, firmware, or some other form of computer-readableprocessing instructions. Software 1315 also includes DC module 1316.When executed by processing system 1313, DC module 1316 directs datacontrol system 1300 to operate as described herein.

In some examples, DC module 1316 instructs processing system 1313 todirect communication interface 1311 to receive a request to retrievedata from a primary storage volume that includes a secondary storagevolume. DC module 1316 further instructs processing system 1313 todirect storage system 1314 to store the primary storage volume thatincludes the secondary storage volume. DC module 1316 directs processingsystem 1313 to identify changed segments of a plurality of segments inthe primary storage volume, and identify allocated segments of thechanged segments. DC module 1316 instructs processing system 1313 todirect communication interface 1311 to transfer the allocated segmentsin response to the request.

In some examples, DC module 1316 instructs processing system 1313 to, inresponse to the request to retrieve the data from the primary storagevolume, determine a subset of the plurality of data items that are notlive based on the allocated segments of the changed segments identifiedin the primary storage volume, and execute an operation on the subset ofthe data items to reduce an amount of the plurality of blocks involvedin retrieving the data. In some examples, in order to execute theoperation on the subset of the data items DC module 1316 instructsprocessing system 1313 to delete each data item of the subset of thedata items.

In some examples, DC module 1316 executed by processing system 1313identifies qualified blocks of a plurality of data blocks responsive toreceiving a request for a volume of data having a plurality of datablocks, filters the plurality of data blocks to construct a list ofqualified blocks, and reads the list of qualified blocks from the firstvolume of data based on the list of qualified blocks.

In some examples, DC module 1316 executed by processing system 1313 mayalso read the remaining blocks (i.e., the non-qualified blocks) from anull block module such as, for example, a “/dev/zero” file that providesas many null characters (ASCII NUL, 0x00) as are read from it. Further,in some examples DC module 1316 executed by processing system 1313 coulddirect data control system 1300 to transfer a second volume of datacomprising the qualified blocks read from the data volume and the nullblocks provided from the null block module.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. As a result, theinvention is not limited to the specific embodiments described above,but only by the following claims and their equivalents.

What is claimed is:
 1. A method of operating a data control system, themethod comprising: receiving a request to retrieve data from a primarystorage volume; identifying changed segments of a plurality of segmentsin the primary storage volume; identifying allocated segments of thechanged segments; and transferring the allocated segments in response tothe request.
 2. The method of claim 1 further comprising generating alist of qualified blocks based on the allocated segments of the changedsegments identified in the primary storage volume.
 3. The method ofclaim 2 further comprising reading a plurality of data blocks from theprimary storage volume based on the list of qualified blocks.
 4. Themethod of claim 1 wherein the primary storage volume comprises aplurality of blocks corresponding to a plurality of data items in asecondary storage volume within the primary storage volume.
 5. Themethod of claim 4 further comprising, in response to the request toretrieve the data from the primary storage volume: determining a subsetof the plurality of data items that are not live based on the allocatedsegments of the changed segments identified in the primary storagevolume; and executing an operation on the subset of the data items toreduce an amount of the plurality of blocks involved in retrieving thedata.
 6. The method of claim 5 wherein executing the operation on thesubset of the data items to reduce the amount of the plurality of blocksinvolved in retrieving the data comprises deleting each data item of thesubset of the data items.
 7. The method of claim 6 further comprisingflushing changes to the secondary storage volume after deleting eachdata item of the subset of the data items.
 8. The method of claim 1wherein the primary storage volume includes a secondary storage volumestored thereon, and wherein identifying the allocated segments of thechanged segments comprises identifying the allocated segments of thechanged segments based on an allocation status of a plurality of dataitems contained in the secondary storage volume, wherein the pluralityof data items correspond to the changed segments.
 9. A data controlsystem, the system comprising: a communication interface configured toreceive a request to retrieve data from a primary storage volume thatincludes a secondary storage volume; a storage system configured tostore the primary storage volume that includes the secondary storagevolume; and a processing system configured to identify changed segmentsof a plurality of segments in the primary storage volume and identifyallocated segments of the changed segments; the communication interfacefurther configured to transfer the allocated segments in response to therequest.
 10. The system of claim 9 wherein the processing system isfurther configured to generate a list of qualified blocks based on theallocated segments of the changed segments identified in the primarystorage volume, and read a plurality of data blocks from the primarystorage volume based on the list of qualified blocks.
 11. The system ofclaim 9 wherein the primary storage volume comprises a plurality ofblocks corresponding to a plurality of data items in a secondary storagevolume within the primary storage volume.
 12. The system of claim 11wherein the processing system is further configured to, in response tothe request to retrieve the data from the primary storage volume,determine a subset of the plurality of data items that are not livebased on the allocated segments of the changed segments identified inthe primary storage volume, and execute an operation on the subset ofthe data items to reduce an amount of the plurality of blocks involvedin retrieving the data.
 13. The system of claim 12 wherein theprocessing system configured to execute the operation on the subset ofthe data items to reduce the amount of the plurality of blocks involvedin retrieving the data comprises the processing system configured todelete each data item of the subset of the data items.
 14. The system ofclaim 9 wherein the processing system configured to identify theallocated segments of the changed segments comprises the processingsystem configured to identify the allocated segments of the changedsegments based on an allocation status of a plurality of data itemscontained in the secondary storage volume, wherein the plurality of dataitems correspond to the changed segments.
 15. One or morecomputer-readable storage media having program instructions storedthereon for operating a data control system, wherein the programinstructions, when executed by the data control system, direct the datacontrol system to: receive a request to retrieve data from a primarystorage volume; identify changed segments of a plurality of segments inthe primary storage volume; identify allocated segments of the changedsegments; and transfer the allocated segments in response to therequest.
 16. The one or more computer-readable storage media of claim 15wherein the program instructions further direct the data control systemto generate a list of qualified blocks based on the allocated segmentsof the changed segments identified in the primary storage volume, andread a plurality of data blocks from the primary storage volume based onthe list of qualified blocks.
 17. The one or more computer-readablestorage media of claim 15 wherein the primary storage volume comprises aplurality of blocks corresponding to a plurality of data items in asecondary storage volume within the primary storage volume.
 18. The oneor more computer-readable storage media of claim 17 wherein the programinstructions further direct the data control system to, in response tothe request to retrieve the data from the primary storage volume,determine a subset of the plurality of data items that are not livebased on the allocated segments of the changed segments identified inthe primary storage volume, and execute an operation on the subset ofthe data items to reduce an amount of the plurality of blocks involvedin retrieving the data.
 19. The one or more computer-readable storagemedia of claim 18 wherein the program instructions, in order to directthe data control system to execute the operation on the subset of thedata items to reduce the amount of the plurality of blocks involved inretrieving the data, instructs the data control system to delete eachdata item of the subset of the data items.
 20. The one or morecomputer-readable storage media of claim 19 wherein the programinstructions, in order to direct the data control system to identify theallocated segments of the changed segments, instructs the data controlsystem to identify the allocated segments of the changed segments basedon an allocation status of a plurality of data items contained in thesecondary storage volume, wherein the plurality of data items correspondto the changed segments.